Apparatus and methods for providing a national portal for electronic services

ABSTRACT

Apparatus and methods for providing a single location where an entity may conduct electronic services over a national portal. The entity includes an employer, a state, an employee, or any other entity. The electronic services include employee obligations, employee garnishments, new hire reporting, communications, call center, exception handling, regulation database, other databases, human resources, search engine, payments, disbursements, and future uses. Future uses includes additional users (e.g., additional entities) or additional uses (e.g., additional services).

This application claims priority under 35 U.S.C. §119 based on U.S. Provisional Application No. 60/325,200, filed Sep. 28, 2001, the complete disclosure of which is incorporated herein by reference.

FIELD OF THE INVENTION

The present invention relates to apparatus and methods for providing electronic services. In particular, the present invention relates to apparatus and methods for a national portal to provide electronic services.

BACKGROUND OF THE INVENTION

Currently, employers must access a host of different electronic services to conduct day-to-day operations. These operations include electronic communications, payment requirements, reporting requirements, and other mandatory and permissive payment and reporting obligations. Examples of electronic communications include email and other types of electronic communications. Examples of payment and reporting obligations include the payment of taxes, the payment of employee child support obligations, the payment of employee garnishments, the reporting of newly hired employees, registration of vehicles, and the payment of parking fees or tickets. There is a need for a system that allows an employer to access a single site for these electronic services. There is also a need for a system that allows others (such as employees, states, banks, and others) to access this site.

This invention addresses the need for a system for providing electronic services over a national portal.

SUMMARY OF THE INVENTION

The apparatus and methods consistent with the present invention overcome the shortcomings of conventional systems by providing a single location, or “portal,” where an entity may obtain electronic services.

In an embodiment of the invention, a method for providing electronic services at a national portal may include receiving at the national portal an electronic communication from an employer, interacting with a government agency to process the communication, and processing the communication at the national portal.

Exemplary apparatus and methods consistent with the present invention are recited in the attached claims. It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention, as claimed.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention, as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate several embodiments of the invention and, together with the following description, serve to explain the principles of the invention. In the drawings:

FIGS. 1A-1E are block diagrams of some of the embodiments of a national portal;

FIG. 2A is a block diagram of one embodiment of a national portal for employers;

FIG. 2B illustrates one embodiment of a national portal for employers, which includes employers, states, and projects for employers;

FIG. 2C illustrates the embodiment of the national portal for employers, shown in FIG. 2B, with one embodiment of a group of services offered by this national portal;

FIG. 3 is a block diagram of one embodiment of the modules for the' services offered in the national portal, as shown in FIG. 2C;

FIG. 4 is a block diagram of one embodiment of the employee obligations module, as shown in FIG. 3;

FIG. 5A is a block diagram of one embodiment of an employee obligations module with multiple employers in one state;

FIG. 5B is a block diagram of another embodiment of an employee obligations module with multiple employers in one state;

FIG. 6A is a block diagram of one embodiment of an employee obligations module with multiple employers and multiple states;

FIG. 6B is a block diagram of one embodiment of a debit-based employee obligations module with multiple employers and multiple states;

FIG. 6C is a block diagram of one embodiment of a credit-based employee obligations module with multiple employers and multiple states;

FIG. 6D is a block diagram of one embodiment of a debit- and credit-based employee obligations module with multiple employers and multiple states;

FIG. 6E is a block diagram of another embodiment of an employee obligations module with multiple employers and multiple states;

FIG. 7 is a block diagram of one embodiment of the employee garnishments module, as shown in FIG. 3;

FIG. 8A is a block diagram of one embodiment of an employee garnishments module with multiple employers in one state;

FIG. 8B is a block diagram of one embodiment of an employee garnishments module with multiple employers and multiple states;

FIG. 9 is a block diagram of one embodiment of a new hire reporting module, as shown in FIG. 3;

FIG. 10A is a block diagram of one embodiment of a new hire reporting module, as shown in FIG. 3;

FIG. 10B is a block diagram of another embodiment of a new hire reporting module, as shown in FIG. 10A;

FIG. 10C is a block diagram of another embodiment of a new hire reporting module, as shown in FIG. 10A;

FIG. 11 is a block diagram of one embodiment of a communications module, as shown in FIG. 3;

FIG. 12 is a block diagram of one embodiment of a call center module, as shown in FIG. 3;

FIG. 13 is a block diagram of one embodiment of a exception handling module, as shown in FIG. 3;

FIG. 14 is a block diagram of one embodiment of a regulation database module, as shown in FIG. 3;

FIG. 15 is a block diagram of one embodiment of an other databases module, as shown in FIG. 3;

FIG. 16 is a block diagram of one embodiment of a human resources module, as shown in FIG. 3;

FIG. 17 is a block diagram of one embodiment of a search engine module, a shown in FIG. 3;

FIG. 18 is a block diagram of one embodiment of a payments module, as shown in FIG. 3;

FIG. 19 is a block diagram of one embodiment of a disbursements module, as shown in FIG. 3;

FIG. 20 is a block diagram of one embodiment of a future uses module, as shown in FIG. 3; and

FIG. 21A is a block diagram of one embodiment of a national portal for employers with financial institutions;

FIG. 21B is a block diagram of another embodiment of a national portal for employers with financial institutions; and

FIGS. 22A and 22B are exemplary flow charts of the operation of a national portal for employers with financial institutions consistent with one embodiment of the present invention, as shown in FIG. 21A.

DESCRIPTION OF THE EMBODIMENTS Introduction

The systems and processes consistent with the principles of the present invention as disclosed herein provide for a single location, or “portal,” where an entity located anywhere in the nation may obtain electronic services.

These electronic services may include electronic communications, payment requirements, reporting requirements and other mandatory and permissive payment and reporting obligations. In one embodiment, the portal is a national portal known as the National Employer Service Center (NESC). In one implementation of this embodiment, the NESC is a national portal on the World Wide Web of the Internet. The NESC may provide for processing of applications, databases, and standards that may be utilized by employers, states, employees, banks, and others. The term “state” as used herein means an agency or other portion of a state government, and the term “others” may include any third party. The NESC may be used as a central location for these users to process information, including financial information as well as any other data. However, it should be recognized that these embodiments and implementations are merely exemplary, and other implementations may also be used.

Systems

FIG. 1A is a block diagram of one embodiment of a national portal. As shown in FIG. 1A, national portal 100 may be utilized by employers 110 and by others 120.

FIG. 1B is a block diagram of another embodiment of a national portal. As shown in FIG. 1B, national portal 100 may be accessed by employers 110, states 130, and others 120. In the embodiment of FIG. 1B, employers 110 may access the national portal 100 for electronic services. Some of these services may include services that require interaction with states 130 or other government agencies. National portal 100 as shown in FIG. 1B, therefore, may allow employers 110 to access one or more states 130. Similarly, employers 110 may access other entities 120 via national portal 100. These other entities 120 may include employees, banks, local government agencies, and any other entity.

FIG. 1C is a block diagram of another embodiment of a national portal. As shown in FIG. 1C, employers 110 and states 130 may access national portal 100. In addition, employers 110 and states 130 may access a network 140 connected to national portal 100. In this embodiment, employers 110 and states 130 may access national portal 100 directly, or via network 140 (such as the Internet or any other network). Therefore, in this embodiment, employers 110 and states 130 may have at least two ways to access the national portal. However, other ways may also be used. For example, in addition to a direct connection or an indirect connection via network 140, employers 110 and states 130 (and any other entity 120) may also access the national portal by other ways, such as, for example, a dial-up connection, FTP, e-mail, e-mail using an attachment, delivery of a tape, delivery of paper, or by facsimile. Other ways of transmission are also included within the scope of the invention.

FIG. 1D is a block diagram of another embodiment of a national portal.

As shown in FIG. 1D, employers 110 and states 130 may have access to the national portal directly or via the network, as shown in FIG. 1C. In FIG. 1D, however, employers 110 and states 130 may have both direct access to national portal 100 and indirect access to national portal 100 via network 140. FIG. 1D also illustrates that more than one employer and more than one state may have access to the national portal. As shown in FIG. 1D, employer₁ 112 and state₁ 132 may have direct access to national portal 100. However, employer_(n) 114 may have access to national portal 100 via network 140, and state_(n) 134 may also have access to national portal 100 via network 140. As shown in FIG. 1D, moreover, any number of employers (employers_(n) 114) or any number of states (states_(n) 134) may have access to national portal 100, either directly (not shown) or via network 140 (shown).

FIG. 1E is a block diagram of another embodiment of a national portal. As shown in FIG. 1E, employers 110 and states 130 may have direct access to national portal 100, and employers 110 and states 130 may have indirect access to the national portal via network 140. FIG. 1E also shows that other users 120 may have access to the national portal, either direct access or indirect access via the network. Other users₁ 122 may have direct access to national portal 100, and other users_(n) 124 may have indirect access to national portal 100 via the network 140. FIG. 1E also shows that national portal 100 may contain one or more projects 102. Project 102 at national portal 100 may include an application such as garnishment of wages, or other type of activity that may be performed by national portal 100 for employers 110, states 130, or other users 120.

FIG. 2A is a block diagram of one embodiment of a national portal for employers 200. As shown in FIG. 2A, employers 210, states 220, and projects for employers 230 may access national portal for employers 200. Employers 210 may access the national portal for employers 200 for services that are available to employers, e.g., projects for employers 230. Some of the services may require interactions with states, and therefore states 220 also may have access to the national portal for employers. Projects for employers 230 may include various applications such as garnishment of wages, and other services that are needed by employers. Employers 210 may access national portal 200 to initiate, process, and/or terminate projects for employers 230. As shown in FIG. 2A, national portal for employers 200 may provide a single location for many employers 210 to access projects for employers 230. Similarly, national portal for employers 200 provides a single location for employers 210 to access states 220. Notably, states 220 may access national portal for employers 200, regardless whether these states need to access an employer (or an employer needs to access a state).

FIG. 2B illustrates another embodiment of a national portal for employers 200, which may include employers, states, and projects for employers. The illustration in FIG. 2B depicts the universe in which national portal for employers 200 functions. As shown in FIG. 2B, there may be a universe of states 220 in which there are smaller universes. One universe that exists within the universe of states 220 may include a universe of employers 210. The universe of employers 210 may exist completely within the universe of states 220. Within the universe of employers 210, there may also be a universe of projects for employers 230. The universe of projects for employers 210 may exist within the universe of employers 210. Within the universe of projects for employers 230, there may be national portal for employers 200. National portal for employers 200 is depicted as not including all projects for employers. However, in another embodiment, the national portal for employers 200 may include all projects for employers 230.

FIG. 2C illustrates the embodiment of the national portal for employers 200, shown in FIG. 2B, with one example of a group of services offered by this national portal. As shown in FIG. 2C, the services offered by national portal for employers 200 may include employee obligations 240, employee garnishments 242, new hire reporting 244, communications 246, call center 248, exception handling 250, regulation database 252, other databases 254, human resources 255, search engine 256, payments 258, disbursements 260, and future uses 262. National portal for employers 200 depicted in FIG. 2C may include other services (not shown). As shown in FIG. 2C, states 220, employers 210, and projects 230 for employers may all interact with national portal 200, which may include one or more of the services.

FIGS. 2B and 2C show that the universe of employers 210 may exist within the universe of states. However, in other embodiments (not shown), national portal 200 for employers may include employers 210 who are not within the universe of states 220. Similarly, other entities (including governmental or nongovernmental entities) may also interact with the national portal for employers. In addition, FIGS. 2B and 2C depicts projects for employers, which may suggest that the projects are only for employers. However, in other embodiments (not shown), the projects that may be implemented through the national portal for employers may be projects for entities other than employers. As noted above, the national portal may also be used by entities other than employers (such as, for example, states, employees, banks, and any other entity).

FIG. 3 is a block diagram of one embodiment of the modules for the services offered in a national portal. Like FIG. 2C, FIG. 3 depicts the services that are available through a national portal for employers 300. However, FIG. 3 denotes that each of these services may be implemented by individual modules. Other embodiments may implement these services in other ways. As shown in FIG. 3, national portal for employers 300 may include employee obligations module 310, employee garnishments module 312, new hire reporting module 314, communications module 316, call center module 318, exception handling module 320, regulation database module 322, other databases module 324, search engine module 326, payments module 328, disbursements module 330, and future uses module 332. Each of these modules is described herein. As indicated by future uses module 322, national portal for employers 300 contemplates that other modules may be readily added.

FIG. 4 is a block diagram of one embodiment of employee obligations module 310, as shown in FIG. 3. As shown in FIG. 4, employee obligations module 310 may include child support obligations 410 and other obligations 420. Child support obligations 410 may be processed as described in U.S. Pat. Nos. 5,946,669 and 6,119,107. Child support obligations 410 may also be processed by other methodologies. Employee obligations module 310 may also process other obligations 420 (e.g., alimony obligations).

In one implementation of employee obligations module 310, an employer may collect obligations owed by an employee of the employer for processing through the national portal. One example of an obligation by an employee that may be processed by the employer through the national portal is a child support obligation. In one implementation, the employer may transmit the child support obligation owed by the employee to the national portal for processing. In this implementation, the child support obligation may be transmitted directly to the national portal (as shown in FIG. 1D) or may be transmitted to the national portal via a network (also as shown in FIG. 1D).

FIG. 5A is a block diagram of one embodiment of employee obligations module 310 with multiple employers in one state. As shown in FIG. 5A, employee obligations module 310 may include multiple employers but only one state. Employee obligations module may include employer₁ 510, employer₂ 520, and employer_(n) 530. Employee obligations module may also include any one state 540. As shown in FIG. 5A, employer₁ 510, employer₂ 520, employer_(n) 530 and any one state 540 may communicate with employer obligations module 310, and employee obligations module 310 may communicate with any of these entities. As shown in FIG. 5A, any number of employers may interact with employee obligations module 310. However, in this one embodiment, only one state (any one state 540) may communicate with employee obligations module 310.

FIG. 5B is a block diagram of another embodiment of an employee obligations module 550 with multiple employers in one state. As shown in FIG. 5B, the employee obligations module may be specific to a particular state. Here, the employee obligations module may include a Michigan employee obligations module 550. Thus, as shown in FIG. 5B, employer₁ 560, employer₂ 570, and employer_(n) 580 may interact with Michigan employee obligations module 550. As indicated by employer_(n) 580, any number of employers in Michigan may interact with Michigan employee obligations module 550. The State of Michigan 590 also may interact with the Michigan employee obligations module.

FIG. 6A is a block diagram of one embodiment of employee obligations module 310 with multiple employers and multiple states. As shown in FIG. 6A, employer₁ 610, employer₂ 612, and employer_(n) 614 may interact with employee obligations module 310. Also, state₁ 620, state₂ 622, and state_(n) 624 may also interact with employee obligations module 310. As shown in FIG. 6A, any number of employers (employer_(n) 614) and any number of states (state_(n) 624) may interact with employee obligations module 310. Alternatively, multiple employee obligation modules, each specific to one or more states may be included in national portal 200, with employers and states being automatically connected to the appropriate employee obligations module.

FIG. 6B is a block diagram of one embodiment of a debit-based employee obligations module with multiple employers and multiple states. As shown in FIG. 6B, employer₁ 610, employer₂ 612, and employer_(n) 614 may interact with debit-based employee obligations module 600, and state₁ 620, state₂ 622, and state_(n) 624 may also interact with debit-based employee obligations module 600. As shown in FIG. 6B, any number of employers (employer_(n) 614) or any number of states (state_(n) 624) may interact with debit-based employee obligations module 600. Notably, employee obligations module 600 in FIG. 6B may include a debit-based employee obligation module. Therefore, any financial information processed by debit-based employee obligations module 600 may be processed as a debit transaction.

FIG. 6C is a block diagram of one embodiment of a credit-based employee obligations module with multiple employers and multiple states. As shown in FIG. 6C, employer₁ 610, employer₂ 612, and employer_(n) 614 may interact with credit-based employee obligations module 630, and state₁ 620, state₂ 622, and state_(n) 624 may also interact with credit-based employee obligations module 630. As shown in FIG. 6C, any number of employers (employer_(n) 614) or any number of states (state_(n) 624) may interact with credit-based employee obligations module 630. In contrast to the debit-based employee obligations module of FIG. 6B, credit-based employee obligations module 630 may process financial information as credit transactions.

FIG. 6D is a block diagram of one embodiment of a debit- and credit-based employee obligations module with multiple employers and multiple states. As shown in FIG. 6D, employer₁ 610, employer₂ 612, and employer_(n) 614 may interact with debit- and credit-based employee obligations module 640, and state₁ 620, state₂ 622, and state_(n) 624 may also interact with debit- and credit-based employee obligations module 640. As shown in FIG. 6D, any number of employers (employer_(n) 614) or any number of states (state_(n) 624) may interact with debit- and credit-based employee obligations module 640. In contrast to the employee obligations module of FIGS. 6B-6C, debit- and credit-based employee obligations module 640 may process financial information as either debit transactions or credit transactions.

FIG. 6E is a block diagram of another embodiment of an employee obligations module 650 with multiple employers and multiple states. As shown in FIG. 6E, employer₁ 610 and employer_(n) 614 may interact with employee obligations module 650, and state₁ 620, state₂ 622, and state_(n) 624 may also interact with employee obligations module 650. In addition, as shown in FIG. 6E, obligor₁ 660 and obligor_(n) 662 may also interact with employee obligations module 650. Obligor₁ 660 and obligor_(n) 662 may represent an employee of an employer that owes an obligation. In addition to child support payments, as described above, obligations owed by an obligor may include alimony or any other obligation. Employee obligation module 650 in FIG. 6E may process financial information as debit-based transactions, credit-based transactions, or a combination of debit- and credit-based transactions. Other processing architectures may also be used by the employee obligations module.

FIGS. 6A-6E depict one set of embodiments of a normal developmental progression that could be used by a national portal with an employee obligations module. For example, a national portal may begin with the employee obligations module depicted in FIG. 6A, then develop the debit-based employee obligations module of FIG. 6B, then develop the credit-based employee obligations module of FIG. 6C, then develop the debit- and credit-based employee obligations module of FIG. 6D, and finally, develop the employee obligations module of FIG. 6E. Of course, other development schemes also may be used to develop an employee obligations module for a national portal. Similarly, other employee obligations modules may be used.

FIG. 7 is a block diagram of one embodiment of employee garnishments module 312, as shown in FIG. 3. As shown in FIG. 7, employee garnishments module 312 may include debts 700, judicial decrees 710, and other garnishments 720. In one embodiment, employee garnishments module 312 may process financial information for a state. For example, a state may send garnishment information to employee garnishments module 312 at the national portal, and then the national portal may process the garnishment against the salary of the employee at the employer.

In another embodiment, employee garnishments module 312 may process financial information for an employee. For example, an employee may have a debt 700, for which the employee wishes to have a garnishment made from the employee's salary. In this circumstance, the employee may access employee garnishments module 312 at the national portal to implement the garnishment of the employee's salary. Employee garnishment module 312 at the national portal may then process the garnishment with the employer for the employee. In still another embodiment, a court may issue a judicial decree 710 to garnish an employee's salary through the national portal using employee garnishments module 312. In this circumstance, a court may inform employee garnishments module 312 at the national portal of the court-ordered garnishment. Employee garnishments module 312 at the national portal may then process the garnishment against the salary of the employee at the employer. Other garnishments 720 may also be implemented by the employee garnishments module.

FIG. 8A is a block diagram of one embodiment of employee garnishments module 312 with multiple employers and one state. As shown in FIG. 8A, employee garnishments module 312 may be accessed by employer₁ 800, employer₂ 802, and employer_(n) 804. As indicated on FIG. 8A, any number of employers (employer_(n) 804) may access employee garnishments module 312. Employee garnishments module 312 may also be accessed by any one state 810. In this embodiment, only one state (any one state 810) may access employee garnishments module 312.

FIG. 8B is a block diagram of one embodiment of employee garnishments module 312 with multiple employers and multiple states. As shown in FIG. 8B, employee garnishments module 312 may be accessed by employer₁ 800, employer₂ 802, and employer_(n) 804, and employee garnishments module 312 may also be accessed by state₁ 810, state₂ 812, and state_(n) 814. In contrast to FIG. 8A, the employee garnishments module in FIG. 8B may be accessed by any number of employers (employer_(n) 804) and any number of states (state_(n) 814). Additionally, as referenced above (but not shown), the employee garnishments module may also be accessed by any other entity 720 (such as a court).

FIGS. 8A-8B depict various embodiments of employee garnishments modules by a national portal. In one implementation of these modules, the withholding of the garnishment from an employee's salary may be accomplished through an electronic format. One format for performing this transaction is defined by the American National Standards Institute (ANSI) and the Federal Office of Child Support Enforcement (FOCSE). Other ways may also be used to accomplish the garnishment through an electronic format. Additionally, non-electronic ways may also be used to process the garnishments by the national portal.

FIG. 9 is a block diagram of one embodiment of new hire reporting module 314, as shown in FIG. 3. As shown in FIG. 9, new hire reporting module 314 may be accessed by employers 900, new employees 910, immigration agencies 920, and other entities 930. In one embodiment, new hire reporting module 314 may be used by employers 900 to report new employees 910 that have been hired. Under the Personal Responsibility and Work Opportunities Reconciliation Act of 1996, in certain circumstances, employers must report the hiring of new employees within 20 days of hiring. Using new hire reporting module 314, employers 900 may report the hiring of employees 910, and the new hire reporting module will then automatically transmit this information to all of the necessary reporting agencies (whether state, municipal, or any other governmental or non-governmental entity). In other embodiments, new employees 910, immigration 920, and other entities 930 may also access new hire reporting module 314 to report the hiring of new employees 910. In still other embodiments, new hire reporting module 314 may be used to report terminations of employment. New hire reporting module 314 may also have other functions.

FIG. 10A is a block diagram of another embodiment of new hire reporting module 314, as shown in FIG. 3. As shown in FIG. 10A, new hire reporting module 314 may be accessed by any employer 1000, any payroll service 1010, state₁ 1020, state₂ 1022, and state_(n) 1024. As explained earlier, other entities may also access the new hire reporting module (not shown). Any employer 1000 may access the new hire reporting module 314 to report the hiring of a new employee. Similarly, any payroll service 1010 may also access the new hire reporting module 314. Some payroll services 1010 may automatically record and prepare information regarding the hiring of new employees, and these payroll services may be able to automatically interact with new hire reporting module 314. Any number of states 1020, 1022, and 1024 may also be able to access new hire reporting module 314, and new hire reporting module 314 may also be able to access any number of states 1020, 1022, and 1024. The access between new hire reporting module 314 and various states 1020, 1022, and 1024 will allow the information provided by employers or payroll services to be transmitted to the states. States 1020, 1022, and 1024 may also be able to access new hire reporting module 314, should the states have questions regarding the information transmitted from the employers or from the payroll services.

FIG. 10B is a block diagram of another embodiment of new hire reporting module 314, as shown in FIG. 10A. As shown in FIG. 10B, new hire reporting module 314 may be linked to a single group of employers, in this case the employers in Colorado 1030. Similarly, new hire reporting module 314 also may be linked to a single payroll service, in this case PayChex 1040. However, even though one state is listed specifically (in this case, Colorado 1060), any number of states (states_(n) 1050) may access new hire reporting module 314.

FIG. 10C is a block diagram of another embodiment of new hire reporting module 314, as shown in FIG. 10A. As shown in FIG. 10C, any number of employers in any number of states may access this new hire reporting module. Thus, employer₁ in state₁ 1070, employer_(n) in state₁ 1072, employer₁ in state_(n) 1074, and employer_(n) in state_(n) 1076 may all access new hire reporting module 1085. Similarly, any payroll service 1080 may also access new hire reporting module 1085. Any state may also access new hire reporting module 1085, such as state₁ 1090, state₂ 1092, and state_(n) 1094. FIG. 10C also indicates that new hire reporting module 1085 may have an optional feature, including links to new hire reporting websites. This optional feature allows users of the new hire reporting module to locate information from other new hire reporting websites. This optional feature is consistent with the other services available at the national portal, which allow employers and other users of the national portal to find all information at one location, that is, at the national portal.

FIGS. 10A-10C depict one set of embodiments of a normal developmental progression for the creation of a new hire reporting module. A new hire reporting module at a national portal may first include only a single group of employers, as shown in FIG. 10B, or a single type of payroll service, as also shown in FIG. 10B. However, subsequent development may allow the addition of other employers and the addition of other payroll services, as shown in FIG. 10C. Subsequent development may also include additional capabilities. For example, in addition to communications between employers and states (or employers and payroll services, or any other combination of entities to states), the new hire reporting module may also allow the transfer of files either from employers or payroll services to states or from states to employers or payroll services. These files may include information regarding the hiring of new employees or any other information. All of these embodiments of a new hire reporting module, or any combination thereof, are included in the current invention.

FIG. 11 is a block diagram of one embodiment of communications module 316, as shown in FIG. 3. As shown in FIG. 11, communications module 316 may include telephone 1100, electronic 1110, mail 1120, and other types of communication 1130. Communications module 316 includes any capability by which an employer (or any other entity) may access the national portal. Communications module 316 is also the way by which an employer (or any other entity) may make contact with a state (or any other entity), which has access to the national portal. In short, communications module 316 is also the way by which any entity may communicate with another entity through the national portal.

FIG. 12 is a block diagram of one embodiment of call center module 318, as shown in FIG. 3. As shown in FIG. 12, call center 318 may include 800 operators 1200, toll operators 1210, and any other means of accessing the call center module 1220. In one embodiment, the call center module may be the customer support component of the national portal. Users of the national portal may be able to contact individuals at the national portal via the call center module. This contact may be by telephone (800 operators 1200 or toll operators 1210), by e-mail (not shown), or by any other method 1220. Services available at the call center may include registration with the national portal, obtaining information about services at the national portal, technical assistance with the use of the national portal, and other services. In one embodiment, the call center may include live individuals to answer telephones as well as pre-recorded information available to callers. Other embodiments may provide other services to users at the call center.

FIG. 13 is a block diagram of one embodiment of exception handling module 320, as shown in FIG. 3. As shown in FIG. 13, exception handling module 320 may include in-person exception handling 1300, electronic exception handling 1310, telephonic exception handling 1320, and other exception handling 1330. In one embodiment, exception handling module 320 may be used by users of the national portal to validate transactions. If transactions initiated by users are validated, then exception handling module 320 may no longer be needed. However, if the transactions are not validated, exception handling module 320 may provide solutions for resolving the invalid transactions. These solutions may include human interaction by in-person exception handling 1300, the transmission of an e-mail to the user by electronic exception handling 1310, the initiation of a telephone call to the user by telephonic exception handling 1320, or other ways of informing the user that the transaction was rendered invalid by the exception handling module (other exception handling 1330). Exception handling module 320 may also resolve invalid transactions, after the user has contacted the national portal. Exception handling module 320 may further include other functions regarding transactions conducted through the national portal.

FIG. 14 is a block diagram of one embodiment of regulation database module 322, as shown in FIG. 3. As shown in FIG. 14, regulation database module 322 may include child support regulations 1400, garnishment regulations 1410, and other regulations 1420. In one embodiment, regulation database module 322 may provide a source of information regarding regulations that are pertinent to the users of the national portal. For example, a user may need to access child support regulations or garnishment regulations. As users need to access other regulations, the national portal may add those regulations to regulation database module 322, as shown by other regulations. FIG. 14 shows how the national portal provides all of the information that employers (or other users) may need at one location, that location being the national portal. In one embodiment, regulation database module 322 may include regulations from government entities, such as federal regulations or state regulations. However, in other embodiments, other regulations (or even other information) may also be included within regulation database module 322.

FIG. 15 is a block diagram of one embodiment of other databases module 324, as shown in FIG. 3. As shown in FIG. 15, other databases module 324 may include legal information 1500, administrative information 1510, and other information 1520. In one embodiment, users of the national portal may need to access information that is not available in the regulation database module, as shown in FIG. 14. Other databases module 324 may provide a source for other information, such as legal information or administrative information. Legal information 1500 may include tax information or other information. Administrative information 1510 may include department of motor vehicle information or other information. Other information 1520 may further include any type of information that would be of interest to an employer (or other user) of the national portal.

FIG. 16 is a block diagram of one embodiment of human resources module 325, as shown in FIG. 3. As shown in FIG. 16, human resources module 325 may include legal information 1600, administrative information 1610, training information 1620, payroll information 1630, and other information 1640. Human resources module 325 may allow employers (or other users) to update human resource information at the national portal, allowing the information uniform across various departments and readily accessible.

Legal information 1600 may include any legal information, such as information regarding employer legal rights and employee legal rights. Some information may include noncompetition agreements, equal employment information, and information on protection for workers with disabilities. Administrative information 1610 may include any employee data, potential employee data, or company related data, such as employee personal data, employee evaluations, inter-department transfers, job candidate referrals, recruiting information, family leave, company functions, relocation expenses, and travel expenses. Training information 1620 may include information and materials regarding orientation, on-site training, continuing education programs, and any reimbursement for such training. Payroll information 1630 may include any information that would adjust an employee's net take-home pay, such as salary information, tax information, retirement plan contributions by employee and employer, charitable deductions by employee, and employee contributions to employer provided benefit plans including medical, dental, and vision insurance, dependant care assistance, and savings programs for college or medical expenses.

Human resources module 325 may accept legal information 1600, administrative information 1610, training information 1620, payroll information 1630, and other information 1640 and adjust an employee's paycheck accordingly. For example, based on payroll information 1630 provided to human resources 325, an employee who chooses not to receive medical and dental insurance offered by an employer may receive additional money in his paycheck representing an amount saved in insurance fees by the employer. Similarly, an employee who chooses to receive the insurance may receive a deduction in his paycheck to cover at least a portion of the cost. In yet another example, human resources module may accept administrative information 1610 and provide a bonus to employees who refer a job candidate who is subsequently hired.

FIG. 17 is a block diagram of one embodiment of search engine module 326, as shown in FIG. 3. As shown in FIG. 17, search engine module 326 may include global searches 1700, local searches 1710, and other searches 1720. In one embodiment, search engine module 326 may allow an employer (or other user) to perform searches at the national portal. The searches available through the search engine module may include global searches 1700. Global searches may include searches not only done at the national portal but also searches outside of the national portal. The searches available through search engine module 326 may also include local searches 1710. Local searches 1710 may include only searches at the national portal. The searches available through the search engine module may also include other searches 1720. Other searches 1720 may include searches other than global searches 1700 or local searches 1710.

FIG. 18 is a block diagram of one embodiment of payments module 326, as shown in FIG. 3. As shown in FIG. 18, payments module 328 may include electronic payments 1800, paper payments 1810 and other payments 1820. In one embodiment, most payments processed by the national portal may be performed through payments module 328. These payments may be processed either electronically by electronic payments 1800, as a paper document by paper payments 1810, or by any other method by other payments 1820. Other payments 1820 may include payments by facsimile or payments by any other payment methodology. As referenced in FIGS. 6B-6C, in one embodiment, payments processed by the payments module may be either debit-based transactions or credit-based transactions. Notably, in other embodiments, payments need not necessarily be processed by the national portal.

FIG. 19 is a block diagram of one embodiment of disbursements module 330, as shown in FIG. 3. As shown in FIG. 19, disbursements module 330 may include electronic disbursements 1900, paper disbursements 1910, and other disbursements 1920. In one embodiment, most disbursements may be processed by disbursements module 330 as required by the employers (or other users). For example, if a child support payment must be made by the national portal, based upon an obligation owed by an employee to a custodial parent, the disbursements module may make payment to that custodial parent (or to the appropriate state for the benefit of the custodial parent). In one embodiment, disbursements module 330 may make payment either by electronic disbursements 1900 or paper disbursements 1910. Electronic disbursements 1900 may include electronic payment methods, such as electronic funds transfer (EFT). Paper disbursements 1910 may include paper-based methods, such as the transmission of a check. Other disbursements 1920 may also be used by disbursements module 330. One example of another form of disbursement includes the use of a payment card. Disbursements module 330 may issue payment cards, which have a set amount of value. These payment cards may be used to make payments to persons or entities, e.g., to persons who do not have a bank account. Notably, in other embodiments, disbursements need not necessarily be processed by the national portal.

FIG. 20 is a block diagram of one embodiment of future uses module 332, as shown in FIG. 3. As shown in FIG. 20, future uses module 332 may include employees 2000, non-employers 2010, and others 2020. In one embodiment, the users of the national portal may include employers. In other embodiments, there may be other users or additional users, e.g., employers and states. Future uses module 332 may include the other users (or uses) for the national portal. For example, employees 2000 may use the national portal, which would be incorporated into future uses module 332. Similarly, other non-employers 2010 may use the national portal, which would also be included in future uses module 332. Still other users or uses 2020 of the national portal may also be included in future uses module 332. Other uses 2020 of the national portal may include any services other than those listed in FIG. 2C.

Processes

FIG. 21A is a block diagram of one embodiment of a national portal for employers with financial institutions. As shown in FIG. 21A, an employer 2110 may access a national portal for employers 2120 for services needed by the employer. The national portal for employers may include services 2122 and rules 2124. Services 2122 may include the services that are available at the national portal for employers 2120, and rules 2124 may includes the rules that limit the services that are available by the national portal for employers.

Examples of services are shown in FIG. 2C. Examples of rules include the rules for certain payments or financial transactions. One example of rules would include those set by the National Automated Clearing House Association (NACHA), which pertain to the electronic transfer of funds from one entity to another through an ACH. Another example of rules includes the rules pertaining to the American National Standards Institute (ANSI). Another example of rules pertains to the rules for payment order remittance (standard 521 for liens and garnishments). Another examples of rules includes the rules for new hiring reporting (standard 540). The invention includes any type of rules.

As shown in FIG. 21A, national portal for employers 2120 may interact with project 2132, state 2134, and other 2136. Project 2132 may include any project (or any application or any other type of services) that an employer may need to be performed. State 2134 may include any state that may need information from an employer (or that may need to provide information to an employer). Other 2134 may include any interaction with an employer which is different from the interaction needed by project 2132 or state 2134. Project 2132, state 2134, and other 2136 may also interact with a respective bank for financial transactions. For example, for the financial transactions, the processing may include the transfer of data from a source to a bank through an automated clearing house. Thus, project 2132 may connected to project bank 2152 via an ACH 2140, state 2134 may be connected to state bank 2154 via ACH 2140, and other 2136 may be connected to other bank 2156 via ACH 2140.

For financial transactions, the employer may also be connected to an employer bank 2190. Employer 2110 may interact with employer bank 2190 directly (shown) or via an ACH (not shown). Similarly, national portal for employers 2120 may also be connected to a bank for national portal 2170. National portal for employers 2120 may interact directly with bank for national portal 2170 (shown) or via an ACH (not shown). Thus, as shown in FIG. 21A, if employer 2110 needs to make a payment to the national portal for employers 2120, employer 2110 may make that payment through employer bank 2190, which then makes the payment to bank for national portal 2170 via an ACH 2180. Bank for national portal 2170 may then forward the payment to the proper recipient via an ACH 2160, such as to project bank 2152, to state bank 2154, or to other bank 2156.

FIG. 21B is a block diagram of another embodiment of a national portal for employers with financial institutions. As shown in FIG. 21B, the national portal for employers is similar to that shown in FIG. 21A, except FIG. 21B additionally includes an obligor 2194 and obligor bank 2192. Obligor 2194 may be any entity other than an employer (such as an employee, or even a state or other entity) that establishes a financial transaction through national portal for employers 2120. Thereafter, national portal for employers 2120 may process the transaction as described in FIG. 21A.

FIGS. 22A-22B are exemplary flow charts of the operation of a national portal for employers with financial institutions consistent with one embodiment of the present invention, as shown in FIG. 21A. As shown in FIG. 22A, the operation of a national portal for employers includes a number of steps. The steps depicted in FIG. 22A are only one example of one embodiment of the operation of the national portal. Other methodologies for the operation of the national portal (not depicted) are also within the scope of the present invention, examples of which are illustrated in part by FIGS. 1-21.

As shown in FIG. 22A, the employer first furnishes employee information to the national portal (step 2205). This employee information may include new hire information, information regarding an employee obligation, or any other information. The national portal then transfers the employee information to the proper entity (step 2210). The proper entity to receive the employee information depends on the information. For example, step 2210 may include sending the information to the project (step 2212), to the state (step 2214), or the other entity (step 2216). Once the employee information has been transmitted from the national portal to the project, state, or other entity, an instruction is generated by the proper entity and returned to the national portal (step 2215). An example of an instruction would be a garnishment against a salary of the employee. The instruction is then transferred from the national portal to the employer (step 2220).

As shown in FIG. 22B, after the national portal has transferred the instruction to the employer, the employer receives the information e.g., garnishment information (step 2225). The employer then generates a payment and payment information for the instruction (step 2230). The employer then transmits the payment to the employer bank (step 2232), and then, the employer bank transmits the payment to the bank for the national portal via an ACH (step 2236). The employer also transmits the payment information to the national portal (step 2234), and then, the national portal transmits the payment information to the proper entity (step 2238). In transmitting the payment information to the proper entity, the national portal transmits the payment information either to the project (step 2242), the state (step 2244), or the other entity (step 2246). The payment information is then transferred via an ACH (step 2248). Finally, the payment information is transferred to the proper bank for the proper entity, either project bank (step 2252), state bank (step 2254), other bank (step 2256).

Following the transmission of the payment information from the national portal to the proper entity, the payment is then processed by the national portal, when the national portal authorizes the payment to be made to the proper entity (step 2260). When the national portal authorizes payment to the proper entity, the national portal informs the bank for national portal that the payment is authorized. The bank for national portal then processes the payment to the bank for the proper entity (step 2270). In this step, the bank for national portal sends the payment either to a project bank (step 2272), a state bank (step 2274), or other bank (step 2276).

Notably, as described in more detail above, payment processing according to the invention may occur by debit-based processing or by credit-based processing. Additionally, the order of any of these steps may be changed without departing from the scope of the invention.

Other embodiments of the invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the invention being indicated by the following claims. 

1.-27. (canceled)
 28. A method for processing an employee garnishment for an employer at a national portal, comprising: receiving employee garnishment information of an employee from a third party at the national portal; receiving salary information of the employee from the employer at the national portal; and processing the garnishment against a salary of the employee at the national portal.
 29. The method of claim 28, wherein the third party comprises at least one of a state, an employee, and a court.
 30. The method of claim 28, wherein the garnishment comprises one of a debt and a judicial decree.
 31. The method of claim 28, wherein the garnishment is processed electronically.
 32. The method of claim 28, wherein the garnishment is processed by non-electronic means. 33.-69. (canceled)
 70. A system for processing an employee garnishment for an employer at a national portal, comprising: a garnishment receive component for receiving employee garnishment information of an employee from a third party at the national portal; a salary receive component for receiving salary information of the employee from the employer at the national portal; and a processor for processing the garnishment against a salary of the employee at the national portal.
 71. The system of claim 70, wherein the third party comprises at least one of a state, an employee, and a court.
 72. The system of claim 70, wherein the garnishment comprises one of a debt and a judicial decree. 73.-86. (canceled)
 87. A system for processing an employee garnishment for an employer at a national portal, comprising: means for receiving employee garnishment information of an employee from a third party at the national portal; means for receiving salary information of the employee from the employer at the national portal; and means for processing the garnishment against a salary of the employee at the national portal. 88.-93. (canceled)
 94. A computer program product for processing an employee garnishment for an employer at a national portal, the computer program product comprising the following computer-readable program code for effecting actions in a computing platform: program code for receiving employee garnishment information of an employee from a third party at the national portal; program code for receiving salary information of the employee from the employer at the national portal; and program code for processing the garnishment against a salary of the employee at the national portal.
 95. (canceled)
 96. A computer program product for providing electronic services at a national portal for an employer, the computer program product comprising the following computer-readable program code for effecting actions in a computing platform: program code for receiving employee information from the employer at the national portal; program code for transferring the employee information from the national portal to a third party; program code for receiving an instruction at the national portal from the third party based upon the employee information; program code for transferring the instruction from the national portal to the employer; program code for receiving payment information from the employer at the national portal based on the instruction; program code for transmitting the payment information from the national portal to the third party; and program code for processing a payment at the national portal from the employer to the third party. 